The Allocation module summarizes the token inventory for a virtual server. The transaction log displays a detailed list of all allocations and deallocations related to an account.

Account managers can allocate tokens and capacity.

1. On the STA Token Management console, select Snapshot > Allocation.

   

   The allocation table includes the following information:

   • Maximum—This lists the maximum number of users that can authenticate against the server. Users can have multiple tokens and the total number of tokens issued to users can exceed server capacity. In all cases, these values are decremented as capacity and tokens or authentication methods are consumed. Some authentication methods consume the same resource. For example, all tokens consume a unit of capacity when assigned to a user. Likewise, SMS, GrIDsure, and passwords consume a token license, therefore every time any one of these token or authentication methods is assigned to a user, totals for each token type in this class are decremented.

   Prior to v3.2, capacity determined the maximum number of tokens or authentication methods that could be assigned to users.

   • In Use—This lists the capacity consumed as well as totals for all token or authentication methods that are in use.

   • Available—This lists the capacity and tokens that are available for assignment to users.

View the transaction log

1. On the STA Token Management console, select Snapshot > Allocation.

   

2. Select Transaction Log.

   The transaction log lists the following information:

   • Transaction ID—This is a unique number assigned by the server to each allocation by the service provider. The transaction ID is a hyperlink if the transaction includes tokens. Clicking the hyperlink displays a list of all tokens by serial number included in the transaction.

   • Reference—This is a value entered by the service provider when allocating the token, generally to aid in identifying the transaction when communicating with the account. This value may have meaning only to the service provider.

   • Allocate to—This is the account which received the inventory allocation. For example, when a service provider allocates inventory, the value in this field will be the name of the account that received the inventory. Conversely, during deallocation inventory is returned to the service provider and therefore the service provider name will appear in this field.

   • Allocated From—This is the account that allocated the inventory. The values in this field are the opposite of Allocate to.

   • Date—This is the date and time of the allocation.

   • Quantity—This indicates the item quantity of the transaction, usually tokens or SMS credits.

   • Product—This indicates the primary item in the transaction. If the transaction contains tokens, this will display the token family such as KT, RB etc. A transaction cannot contain more than one token type.

   • Type—This indicates Rental or Sale. Rental indicates that the allocation of tokens or authentication methods is part of a subscription, incurring a periodic charge for usage. Sale indicates that tokens or authentication methods have been purchased.

   • Capacity—This indicates the quantity of capacity included in the transaction. Note that capacity is always a rental transaction even when included in a transaction with tokens marked as Sale.

   • Changed by—This is the name of the account manager that performed the allocation.

Any transaction that came from a parent to a child can be used to allocate tokens to the child’s child if, and only if, all tokens, capacity, and credits that came with the transaction from the parent are available to be allocated.